refactor(evm): add TransactionKey wrapper#1331
Merged
Merged
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #1331 +/- ##
===========================================
+ Coverage 57.82% 58.13% +0.31%
===========================================
Files 967 971 +4
Lines 64474 64983 +509
Branches 1680 1762 +82
===========================================
+ Hits 37283 37781 +498
- Misses 26951 26960 +9
- Partials 240 242 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
sebastijankuzner
force-pushed
the
refactor/evm/transaction-key-wrapper
branch
3 times, most recently
from
35e5eea to
9c676e5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Change the transaction key used for storage to make it possible to implement more efficient range scans. The previous implementation sorted lexicographically instead of numerically.
Checklist